Please address the comments from this code review:

## Overall Comments
- The magic string '__astrbot_follow_config__' is repeated in multiple places on the frontend; consider extracting it into a shared constant to avoid typos and make future changes easier.
- You added `batchTtsProviderOptions` but the batch TTS select still appears to use the original `ttsProviderOptions`; please confirm the correct options source is wired up or remove the unused computed to avoid confusion.
- Enabling `config.use_reloader = True` in `server.py` affects runtime behavior and may not be desirable in non‑development environments; consider making this conditional on an environment flag or local dev setting.

## Individual Comments

### Comment 1
<location path="dashboard/src/views/SessionManagementPage.vue" line_range="674" />
<code_context>
     chatProviderOptions() {
       return [
-        { label: this.tm('provider.followConfig'), value: null },
+        { label: this.tm('provider.followConfig'), value: '__astrbot_follow_config__' },
         ...this.availableChatProviders.map(p => ({
           label: `${p.name} (${p.model})`,
</code_context>
<issue_to_address>
**suggestion:** Extract the follow-config sentinel string into a shared constant to avoid duplication and typo risk.

The `'__astrbot_follow_config__'` literal appears in several places (defaults, options, checks). Please define a single shared constant (e.g. `const FOLLOW_CONFIG_SENTINEL = '__astrbot_follow_config__'` or a `data`/`computed` property) and reference it everywhere to avoid typos and simplify future changes.

Suggested implementation:

```
const FOLLOW_CONFIG_SENTINEL = '__astrbot_follow_config__'

        chat_completion: FOLLOW_CONFIG_SENTINEL,
        speech_to_text: FOLLOW_CONFIG_SENTINEL,
        text_to_speech: FOLLOW_CONFIG_SENTINEL,
      },

      // 插件配置

    chatProviderOptions() {
      return [
        { label: this.tm('provider.followConfig'), value: FOLLOW_CONFIG_SENTINEL },
        ...this.availableChatProviders.map(p => ({
          label: `${p.name} (${p.model})`,
          value: p.id

    sttProviderOptions() {
      return [
        { label: this.tm('provider.followConfig'), value: FOLLOW_CONFIG_SENTINEL },
        ...this.availableSttProviders.map(p => ({
          label: `${p.name} (${p.model})`,
          value: p.id

```

1. Place the `const FOLLOW_CONFIG_SENTINEL = '__astrbot_follow_config__'` declaration at the top of the `<script>` block (or just after existing imports) to match your project's conventions; the SEARCH/REPLACE block above assumes this snippet is near the top of the script, but you may need to move the constant accordingly.
2. Search the remainder of `SessionManagementPage.vue` for any other occurrences of `'__astrbot_follow_config__'` (e.g. in watchers, computed properties, validation logic) and replace them with `FOLLOW_CONFIG_SENTINEL` as well.
3. If this sentinel is used in other files (e.g. shared stores or components), consider moving `FOLLOW_CONFIG_SENTINEL` into a shared constants module (e.g. `src/constants/providers.ts`) and importing it here and elsewhere to fully centralize the value.
</issue_to_address>

### Comment 2
<location path="astrbot/dashboard/routes/session_management.py" line_range="384-385" />
<code_context>
             if not isinstance(umos, list):
                 return Response().error("参数 umos 必须是数组").__dict__

+            if rule_key and rule_key not in AVAILABLE_SESSION_RULE_KEYS:
+                return Response().error(f"不支持的规则键: {rule_key}").__dict__
+
             # 批量删除
</code_context>
<issue_to_address>
**suggestion:** Consider validating `scope` values explicitly to produce clearer errors for invalid input.

An unsupported `scope` (e.g. a typo) currently just leaves `umos` empty and triggers the generic "缺少必要参数: umos 或有效的 scope" error, which hides that `scope` itself was invalid. Please validate `scope` against the allowed set and return a specific error (e.g. "不支持的 scope 值") before expanding it into `umos` so invalid scopes aren’t treated the same as missing `umos`.

Suggested implementation:

```python
                    elif scope == "all":
                        umos = all_umos

            # 显式校验 scope，避免无效 scope 静默失败
            allowed_scopes = {"all"}
            if scope and scope not in allowed_scopes:
                return Response().error("不支持的 scope 值").__dict__

            if not umos:
                return Response().error("缺少必要参数: umos 或有效的 scope").__dict__

```

To fully align this change with the rest of the function:

1. Update `allowed_scopes` to include all currently支持的 scope 值（例如如果上文有 `if scope == "online"`, `if scope == "selected"` 等分支，请将这些字符串也加入到 `allowed_scopes` 集合中），确保不会误报合法 scope 为无效。
2. If there is a centralized definition of allowed scopes elsewhere in the codebase (e.g. a constant like `AVAILABLE_SESSION_SCOPES`), replace the hardcoded `allowed_scopes` set with that constant to keep things DRY and consistent.
</issue_to_address>